The fact that 0 is a bad default needs to be a addressed too. From my look at the api server source, it always sends back 0 for timeout. And --session-timeout seems to do nothing on the server, as it's only used by cli daemon.

I'm personally making some changes for this (namely adding a default timeout I can put in the config.json file). Not sure how maintainers want it set up, but it's definitely not good the way it is now.

LGTM, thanks! Just noting the continue on 0 subtly falls through to the next key instead of returning immediately, but shouldn't matter in practice 👍

Yeah. The continue behavior is so that it checks all the keys just in case one of them is greater than 0.

Honestly, I don't understand the purpose/origin of the different keys, so not sure if this is even necessary or desirable. 🤷‍♂️